Summary

Fixes two issues found in CI:

1. actionlint false positives in ci-self-test

Root cause: The actionlint job vends .openci/ from a pinned SHA via resolve-openci. When the top-level workflow files reference newer action input names than what exists in the older vendored composite actions, actionlint reports "input not defined" errors.

Fix: Remove the resolve-openci vendoring step from the actionlint job. Actionlint only needs to check the current source files — the vendored .openci/ at a different SHA introduces false positives.

2. test.yml text corruption

Root cause: An earlier version of bump-self-sha.sh used awk '{print $NF}' to extract the old SHA from manifest.yml. On the line YiAgent/OpenCI: "sha" # resolve-openci bootstrap, awk extracted bootstrap instead of the SHA. The perl substitution then replaced bootstrap with the full 40-char SHA, corrupting bootstrapping into a SHA string in 4 locations.

Fix: Restored the original bootstrapping text in all comments, descriptions and step names.

Files Changed

• .github/workflows/reusable-self-test.yml — Remove resolve-openci from actionlint job (+ SHA sync)
• .github/workflows/test.yml — Fix 4 corrupted text instances

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

Greptile Summary

This PR addresses two separate CI problems: false-positive actionlint errors caused by vendoring an older composite-action SHA into the lint job, and four text corruptions in test.yml where the word "bootstrapping" was replaced with a 40-character SHA by a faulty awk field extractor in bump-self-sha.sh.

• reusable-self-test.yml: Drops the resolve-openci step from the actionlint job so the tool validates workflows against the current composite actions rather than an older vendored copy. The pinned SHA in the three remaining resolve-openci steps is advanced to 0fc8c784 (the PR base commit).
• test.yml: Restores "bootstrapping" in four locations — the file header comment, body comment, workflow_dispatch input description, and step name — all of which were overwritten by the SHA bump script reading the wrong awk field.

Confidence Score: 5/5

Both changes are safe to merge — one removes a step that caused false positives, the other restores text that was mechanically corrupted.

The actionlint job change is a targeted removal of a vendoring step whose only effect was injecting stale composite-action definitions into the linter's view. The remaining jobs that still call resolve-openci have their SHA advanced to the current base commit, keeping them consistent. The test.yml edits are pure text restoration with no behavioral impact.

No files require special attention. The bump-self-sha.sh script that originally caused the corruption is not modified here, so if it is still using awk '{print $NF}' on the manifest line it may corrupt text again on the next SHA bump — worth a follow-up fix there.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Before["actionlint job — BEFORE"]
        A1[Checkout source] --> B1[resolve-openci\nvendor .openci/ at old SHA]
        B1 --> C1[Install actionlint]
        C1 --> D1[Run actionlint]
        D1 --> E1["❌ False positives:\nold .openci/ actions have\ndifferent input names"]
    end

    subgraph After["actionlint job — AFTER"]
        A2[Checkout source] --> C2[Install actionlint]
        C2 --> D2[Run actionlint]
        D2 --> E2["✅ Checks current source\nagainst current composite actions"]
    end

    subgraph SHA["SHA Bump — other jobs"]
        F[resolve-openci step\n38435ebe → 0fc8c784\nbase commit of this PR]
    end

_{Reviews (1): Last reviewed commit: "fix(ci): fix actionlint CI failure and t..." | Re-trigger Greptile}